Restore .git pointer file backup for agents that delete it#145
Merged
Conversation
The worktree lock (#144) protects .git/worktrees/NAME/ from gc pruning. But agents with Bash/Write access can still delete the .git POINTER FILE from the worktree directory itself. This backup/restore catches that case. Both protections together: - Lock → prevents gc from pruning metadata directory - Backup → restores pointer file if agent deletes it Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PR #144 added worktree locking to prevent gc pruning. But the .git POINTER FILE in the worktree is still being deleted by agents (they have Bash access). This adds the backup/restore mechanism back alongside the lock.
Both protections:
.git/worktrees/NAME/.gitpointer file if agent deletes itChange type
Related issue
Further fix for #136
How to test
Breaking changes